You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, there is no way to save fields to a Parse.Object using fromJSON, as dirtyKeys doesn't get set.
This can be confusing as at first glance, you would expect the keys to be set as they are defined. However, after the object is fetched, the keys will be null.
it('from json save data', async (done) => {
const json = {
className : 'TestObject',
date: new Date(),
array: [],
object: {},
string: ''
}
const obj = Parse.Object.fromJSON(json);
expect(obj.get('date')).toBeDefined()
expect(obj.get('date')).toBeInstanceOf(Date);
expect(obj.get('array')).toBeDefined()
expect(obj.get('array')).toBeInstanceOf(Array);
expect(obj.get('object')).toBeDefined()
expect(obj.get('object')).toBeInstanceOf(Object);
expect(obj.get('string')).toBeDefined()
expect(obj.get('string')).toBeInstanceOf(String);
await obj.save();
// all keys are defined
await obj.fetch();
// only created at and updated at are defined
expect(obj.get('date')).toBeDefined()
expect(obj.get('date')).toBeInstanceOf(Date);
expect(obj.get('array')).toBeDefined()
expect(obj.get('array')).toBeInstanceOf(Array);
expect(obj.get('object')).toBeDefined()
expect(obj.get('object')).toBeInstanceOf(Object);
expect(obj.get('string')).toBeDefined()
expect(obj.get('string')).toBeInstanceOf(String);
done();
});
This PR allows a 3rd parameter to fromJSON, where you can specify whether the keys should be set to dirty.
constjson={className : 'TestObject',date: newDate(),array: [],object: {},string: ''}constobj=Parse.Object.fromJSON(json,false,true);// now keys will be dirty
Why is it I cannot find the changes in the latest version 3.4.0. The method fromJSON still only takes these parameters: fromJSON(json: any, override?: boolean): T;.
@ChinaeduPascal This may be just a TypeScript issue. I suggest you look into the SDK code and whether the feature has been removed again. The tests in integration/test/ParseObjectTest.js should demo the feature. If not, please open a new issue.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, there is no way to save fields to a Parse.Object using
fromJSON, asdirtyKeysdoesn't get set.This can be confusing as at first glance, you would expect the keys to be set as they are defined. However, after the object is fetched, the keys will be null.
This PR allows a 3rd parameter to
fromJSON, where you can specify whether the keys should be set to dirty.Properly closes #161 and #482